This page describes the Benthic Imaging AUV data processing. It contains a processing diagram, software needed, and assorted more detailed information.
BI AUV Data processing Diagram
This is a version of the AUV CTD Data Flow Diagram that has been adapted for the Benthic Imager AUV project. It describes the intended processes that are being instantiated for the BI AUV.
BI AUV Data Processing Software
The following table lists and briefly describes the software that is needed for BI AUV.
| Application | Purpose | Development Needed (Base) | Development Needed (Images) |
|---|---|---|---|
| Log files | Store data from instruments on vehicle | Verify config files are correct | Camera driver needed, must log metadata |
| Upload Script | Create message to send to portal and tar up data files | Verify correct message creation and all files are included | Add handling of images? |
| AUV Portal | Copy log files to Tornado and construct XML and send to SSDS | Make sure all log files are transferred and XML is correct | Add image handling |
| Ingest | Stores metadata message | No change | No changes |
| Ruminate | Take XML and store in Metadata database | no changes | no changes |
| UpdateBot | Convert log files to NetCDF | Verify NetCDF files OK | Should we do anything with images? |
| Post-process (system TBD) | add metadata to images, calculate best navigation values? | (new) | (new) |
SSDS AUV Portal Information
The portal runs on jeckel, 134.89.12.45. The distribution is managed out of the ssdsadmin account, which has as its home directory /private/var/automount/ssdsadmin. In that directory there is a dev/ directory, which contains auv_ctd/, which contains the distribution. Normally, you can update the distribution from CVS in this directory. The build is then run and the distributions are copied to the /usr/local/auv_bi. Then the jndi.properties and auvportal.properties files are edited to ensure the portal is configured correctly. See the README file in that directory for more information (also look at the README in the /usr/local/auv_ctd directory.
Normally, the portal should just be running. If you execute a 'ps -aux' hopefully you will see an entry for '/bin/sh portal 9011 &' followed by a java command. If it is not running, you can start it by using the following (on jeckel):
cd /usr/local/auv_bi /bin/sh portal 9011 &
Upload script on Benthic Imaging AUV
First you telnet to the dorado machine (IP 134.89.32.106) (see AUV team for username and password) and cd the directory where the script is run
The upload script on the BIAUV is in /home/dorado1/auv-qnx/auv/altex/onboard/scripts.
You can run the script in interactive mode as ./upload.biauv. Alternatively, you can run the script with the mission name (YYYY.MM.DD) and campaign name (AUVBI) on the run line. For example:
./upload.biauv 2010.089.01 AUVBI
The error message "Bad directory specification (AUVBI2009168), skipping..." is a bug in AuvDataXfer.cc (called as 'adx' from the upload script) which luckily has no impact on the script's behavior. The authorities have been notified.
Benthic Imaging AUV Data Flow Diagram (application/octet-stream)
Benthic Imaging AUV Data Flow Diagram (text/xml)
Benthic Imaging AUV Data Flow Diagram (text/xml)
Benthic Imaging AUV Data Flow Diagram (application/octet-stream)
Benthic Imaging AUV Data Flow Diagram (application/octet-stream)
Benthic Imaging AUV Data Flow Diagram (application/octet-stream)
Benthic Imaging AUV Data Flow Diagram (application/octet-stream)
Benthic Imaging AUV Data Flow Diagram (application/octet-stream)
Benthic Imaging AUV Data Flow Diagram (application/octet-stream)
Benthic Imaging AUV Data Flow Diagram (application/octet-stream)
Benthic Imaging AUV Data Flow Diagram (application/octet-stream)
